docs: fix ISR guide link to res.revalidate#89342
Merged
lukesandberg merged 3 commits intovercel:canaryfrom Feb 5, 2026
Merged
Conversation
Collaborator
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
bgub
pushed a commit
to bgub/next.js
that referenced
this pull request
Feb 5, 2026
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: For Contributors Improving Documentation • [x] Run pnpm prettier-fix to fix formatting issues before opening the PR. • [x] Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide Fixing a bug • [ ] Related issues linked using fixes #number • [ ] Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs • [ ] Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md Adding a feature • [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) • [ ] Related issues/discussions are linked using fixes #number • [ ] e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) • [ ] Documentation added • [ ] Telemetry added. In case of a feature if it's used or not. • [ ] Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md For Maintainers • [ ] Minimal description (aim for explaining to someone not on the team to understand the PR) • [ ] When linking to a Slack thread, you might want to share details of the conclusion • [ ] Link both the Linear (Fixes NEXT-xxx) and the GitHub issues • [ ] Add review comments if necessary to explain to the reviewer the logic behind a change What? Fix a broken link in the ISR guide by switching to a site-absolute /docs/... URL for the res.revalidate reference. Why? Without the leading /, the link can resolve as a relative path and break depending on where it’s rendered. How? Update the ISR guide link target to a site-absolute /docs/pages/guides/incremental-static-regeneration#on-demand-validation-with-resrevalidate. Closes NEXT- Fixes # -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.